stack buffer overflow造句

例句与造句

1. Stack buffer overflow can be caused deliberately as part of an attack known as stack smashing.
2. A NOP-sled is the oldest and most widely known technique for successfully exploiting a stack buffer overflow.
3. For this reason, this is the technique most commonly used in Internet worms that exploit stack buffer overflow vulnerabilities.
4. While this method definitely makes the canonical approach to stack buffer overflow exploitation fail, it is not without its problems.
5. Stack buffer overflow can be caused deliberately as part of an attack known as "'stack smashing " '.
6. It's difficult to find stack buffer overflow in a sentence. 用stack buffer overflow造句挺难的
7. Stack canaries, named for their analogy to a canary in a coal mine, are used to detect a stack buffer overflow before execution of malicious code can occur.
8. If the address of the user-supplied data used to effect the stack buffer overflow is unpredictable, exploiting a stack buffer overflow to cause remote code execution becomes much more difficult.
9. If the address of the user-supplied data used to effect the stack buffer overflow is unpredictable, exploiting a stack buffer overflow to cause remote code execution becomes much more difficult.
10. The " jump to register " technique allows for reliable exploitation of stack buffer overflows without the need for extra room for a NOP-sled and without having to guess stack offsets.
11. This technique can greatly increase the difficulty of exploiting a stack buffer overflow because it forces the attacker to gain control of the instruction pointer by some non-traditional means such as corrupting other important variables on the stack.
12. Typically, buffer overflow protection modifies the organization of stack-allocated data so it includes a " canary " value that, when destroyed by a stack buffer overflow, shows that a buffer preceding it in memory has been overflowed.
13. This technique employs the same basic assumptions behind the return-oriented programming technique : an attacker controlling the call stack, for example through a stack buffer overflow, is able to influence the control flow of the program through simple instruction sequences called " gadgets ".
14. He is also known as the author of the article " Smashing The Stack For Fun and Profit ", published in 1996 " Phrack " magazine issue 49, which was the first high-quality, public, step-by-step introduction to stack buffer overflow vulnerabilities and their exploitation.
15. In a classical attack taking advantage of a stack buffer overflow, the input given to a vulnerable program is crafted and delivered so that it itself becomes executed as cannot be executed directly like this, the input may instead take the form of pointers into pieces of existing program code that then become executed in an unexpected order to generate the functionality of the exploit.
16. In a language with free pointers or non-checked array writes ( such as in C ), the mixing of control flow data affecting the execution of code ( return addresses or saved frame pointers ) and simple program data ( parameters or return values ) in a call stack is a security risk, possibly exploitable through stack buffer overflows as the most common type of buffer overflows.